Release 10.1A: OpenEdge Development:
Programming Interfaces

Recording application events

OpenEdge provides core support for different types of auditing events at three basic levels of auditing:

Raw database record — Raw database record events (or database events) are OpenEdge-defined events that identify basic database operations (such as reading and writing records) and any attempts to perform such operations by an application. OpenEdge records raw database record events as specified in the active audit policies or as required by the OpenEdge auditing framework.
Internal — Internal events are OpenEdge-defined events that identify actions that occur directly or indirectly as a result of session execution (such as authenticating or asserting a user ID). These include actions such as running database utilities, changing the database schema, and so on. OpenEdge records internal events as specified in the active audit policies or as required by the OpenEdge auditing framework.
Application — Application events are events that you can define to OpenEdge for the purpose of identifying application-specific actions not otherwise identified by internal or database events (such as reading certain tables or selecting certain menu options). These also include events for adding context to raw database record events. You must invoke the recording of application events at appropriate points in the control flow of your application. OpenEdge then records these events as specified in the active audit policies.

For more information on the various types of audit events, see OpenEdge Getting Started: Core Business Services . The following sections describe how you can invoke the recording of application events from within the 4GL and how to organize all auditing events, including application events, within various auditing contexts:

Planning application events
4GL for generating application events
Instructing OpenEdge to record an application event
Managing audit event context
Application design considerations